Fix #291 by duongynhi000005-oss · Pull Request #297 · BitgesellOfficial/bitgesell

duongynhi000005-oss · 2026-05-29T03:40:53Z

Fix #291\n\nImplemented the bounty docs.\n\nUpdated:\n- README.md now has a visible section with details.\n- CONTRIBUTING.md now starts with Bitgesell-specific contribution and bounty guidance before the inherited libsecp256k1 notes.\n\nVerified with ; no whitespace issues found. No test suite was run because this is documentation-only.\n\n---\nAuto-generated bounty fix

MyTH-zyxeon · 2026-06-03T04:11:04Z

Maintainers: this looks like a reviewer-friendly docs-only follow-up to the older #291 bounty-hunt documentation lane.

From the current diff, the main acceptance questions seem narrow:

README.md and CONTRIBUTING.md now use Bitgesell-first contribution language instead of the inherited libsecp256k1 heading, which should make the repo's public contribution path much clearer.
The bounty copy stays discretionary (starting at $100 USDT, larger payouts at maintainer discretion), so it does not appear to hard-code a payout promise beyond what maintainers actually approve.
Because the patch is documentation-only, "no test suite run" seems reasonable here, but it would still be useful to confirm that #297 is intended to supersede the earlier closed #291 wording so contributors only have one canonical contribution/bounty blurb.

If that supersession is the intent, this looks close to mergeable as a clean docs/maintainer-onboarding improvement under the Bitgesell bounty lane.

fix: resolve BitgesellOfficial#291

da27442